Visual Studio 2010 Testing Overview
Download as PPTX, PDF0 likes22 views
This document discusses testing capabilities in Visual Studio 2010, including test case management, lab management, exploratory testing, and coded UI testing. It highlights how Visual Studio 2010 aims to align testing with the development lifecycle and enable tighter collaboration between developers and testers. Key capabilities like test case management allow tracking test cases as work items in Team Foundation Server, while lab management helps simplify environment setup and improves test hardware utilization.
Visual Studio 2010 Testing Overview
- 1. Testing with Visual Studio 2010Breaking the walls between developers and testersSteve LangeDeveloper Technology SpecialistMicrosoft | Denver, COstevenl@microsoft.com | blogs.msdn.com/slange
- 2. AgendaIntroductionsMicrosoft’s Approach to TestingTest Capabilities in Visual Studio 2010Test Case ManagementTest Plans, Test Suites, & Test CasesLab ManagementRich & Actionable BugsPerform Exploratory testingCoded UI Test 2
- 3. The State Of SW DevelopmentAn Acceptable Rate of Failure?Based on time, budget, and delivering specified functionality 68% of projects never made it into production or were cancelled 1Can we continue to support this level of Success?2Extreme Chaos, The Standish Group International, Inc. – 2009Average Costoverrun: 45%Average Timeoverrun: 63%Functionalitydelivered on average: 67%2. Extreme Chaos, The Standish Group International, Inc - 2009Source: 1. Dave West, Forrester Research
- 4. Frustrations in development teams4“my testers are spending too long testing the same thing”“tooling is expensive (time, licenses, people)”“the developers say the defects are useless”“when is my software ready to ship?”“we have a changed requirement, what do I need to test?”“developers and testers work in silos and don’t communicate/speak the same language”
- 5. Challenges QA is not aligned with lifecycleDevelopers and testers work in silosQA is not leveraged
- 7. Tester Segmentation70% of testing happens heremajority of test tools target hereblack box testingwhite box testingapi testing
- 12. Goals for 2010 Release - TestingAlign QA with the LifecycleCreate tighter Dev/Test interactionEnable highly leveraged QA teams
- 13. VS 2010 Test Capabilitiesgeneralistspecialistcoded UI testunit testingweb performance testtest runnerload testtest case managementvirtual lab managementdata diagnostic adapters (video, action log, event log etc)team foundation server with reporting(bugs, requirements, user stories, source control, build)
- 14. Visual Studio 2010 Test ComponentsServer ComponentsClient ComponentsLab ManagementSCVMMVM HostLibrary SharesAgentTeam Foundation Server (TFS)Visual Studio 2010 Load AgentLab ManagementMicrosoft Test & Lab Manager (MTLM)Visual Studio ProTFS Web AccessTest Case ManagementControllerBuild ManagementLoad AgentAgentWork Item TrackingSource ControlAgentCollector AgentTarget ServerBuild ServerBuild ServerUpdatedNew
- 16. Key Test Capabilities in VS 201016
- 17. Key Test Capabilities in VS2010
- 19. Test Case ManagementCreate, organize, and run test casesManage a suite hierarchyIncludes “Dynamic” suitesConfigure active iterationsFirst-class Work Items in TFSCan be data-driven19
- 20. Microsoft Confidential20Test Case is first class work item in TFSDetailed steps along with expected results
- 21. Microsoft Confidential21Data drive a test caseSpecify data in parameter table
- 22. Microsoft Confidential22Select common steps and convert to Shared Steps
- 23. Microsoft Confidential23Shared Steps allows for common steps to be reused across test cases
- 26. A tester working in Test and Lab manager can see requirements and tests side-by-sideMicrosoft Confidential26
- 27. He can add existing tests cases to a requirement… Microsoft Confidential27
- 28. …and create new ones with test steps!Microsoft Confidential28
- 29. He runs the test..Microsoft Confidential29
- 30. Which starts up the Test Runner…Microsoft Confidential30
- 31. He can go through the test case step-by-stepMicrosoft Confidential31
- 32. ..and create rich, actionable bugs can be created right from the test…Microsoft Confidential32
- 33. …automatically capturing all the system information…Microsoft Confidential33
- 34. …and the exact steps performed!Microsoft Confidential34
- 35. Back, in Visual Studio, the development team can see the rich bug…Microsoft Confidential35
- 36. …the linked test case...Microsoft Confidential36
- 37. …and the requirement for full traceability!Microsoft Confidential37
- 38. All the while, the team can see progress on requirements as well as the quality of the requirements!
- 39. Lab Management39
- 40. Lab ManagementSimplifies environment setupImproving deployment qualitySimplifies testing multiple configurationsEnables reverting to baseline configurationImproves test hardware utilization
- 41. Lab Management ArchitectureSystem Center Virtual Machine ManagerTeam Foundation Server (TFS)Lab ManagementTest Case ManagementMicrosoft Test & Lab Manager (MTLM)Build ManagementHyper-VHostsVM LibrarySharesWork Item TrackingVM 1Share 1Source ControlVM 2Share 2VM 3Share 3UpdatedNewVM 4Share 441
- 42. Microsoft Confidential42Create Virtual Environment from Lab Center
- 43. Microsoft Confidential43Specify name and location for environment
- 44. Microsoft Confidential44Pick role for VMSelect VM from template library
- 45. Microsoft Confidential45Specify capabilities – “Run Tests” ; “Run Workflows” ; “Network Isolation”
- 46. Microsoft Confidential46Environment (collection of VMs) created
- 47. Microsoft Confidential47Manage snapshots for environmentAccess environment using Lab Environment Viewer
- 48. Lab Management for Distributed TeamLower cost of ownership Now have a visual face to the lab! No waiting - Create machines on a remote site without assistanceGet traction of idle machines using “last accessed time”Friction free – Mark and reserve your machines
- 49. View your lab
- 50. View your lab – Who owns what?
- 51. View your lab – Where are the machines?
- 52. View your lab – who has idle machines?
- 53. Rich & Actionable Bugs53
- 54. Rich & Actionable Bugs54
- 55. WalkthroughFiling Rich & Actionable Bugs
- 56. Microsoft Confidential56Dev clicks on lvr link & selects connect to snapshot of the environment
- 57. Microsoft Confidential57Dev is able to access the snapshot’ed environment via LE viewer
- 59. Exploratory Testing“Wander” application looking for issuesErrors, UX, etc.Turn problems into bugs, then test casesSimple, 1-step test case59
- 61. Coded UI TestMicrosoft Confidential61
- 62. Coded UI TestPuts recorded actions into codeDissects action against executing codeCan be associated against test caseMicrosoft Confidential62
- 63. Microsoft Confidential63From Test->new test, click Coded UI test, specify test name and project name
- 64. Microsoft Confidential64Use existing action recording to generate code
- 65. Microsoft Confidential65Specify test case which has action recording and click OK
- 66. Microsoft Confidential66Code generated from action recording – datasource as TestCase
- 67. Microsoft Confidential67Code generated handles data parameterization
- 68. Microsoft Confidential68Invoke Coded UI Test Builder for adding assertions
- 69. Microsoft Confidential69Drag cross-hair onto the control you want to add assertions on
- 70. Microsoft Confidential70Properties of selected control and its UIMap is shown
- 71. Microsoft Confidential71Select property to assert on and right click to add assertion
- 72. Microsoft Confidential72Add the assert
- 73. Microsoft Confidential73Specify Assert method name and generate code
- 74. Microsoft Confidential74Code generated for assert method
- 75. Microsoft Confidential75Add solution to source control
- 76. Microsoft Confidential76Check-in pending changes
- 77. Microsoft Confidential77Go to test case that you want to associate the newly created automation
- 78. Microsoft Confidential78Specify test method and click OK; save test case
- 80. Reporting binds the teamQuery Work ItemsExcel reportsDashboards
- 81. Create reports in one click
- 82. One Click reports – Team Test
- 83. Show me the test cases that found “good” bugs
- 84. QA Dashboard
- 85. Rich Bugs
- 86. Summary86
- 87. Summary87
- 88. Thank You88